Metadata management convergence platforms, systems and methods

ABSTRACT

Metadata management convergence platforms, systems, and methods to organize a community of users&#39; data records. More specifically, methods managing metadata records related to content housed in unique, disparate or federated holdings in centralized or distributed environments. Also systems and methods for creating and managing metadata records using domain specific language, vocabulary and metadata schema accepted by a community of users of unique, disparate or federated databases in centralized or distributed environments. Such environments can include content repositories including but not limited to: vehicle fleet information systems; government document holdings; insurance and underwriting information holdings; academic library collections; and entertainment archives.

FIELD OF THE INVENTION

The present invention provides metadata management convergenceplatforms, systems, and methods to organize a community of users' datarecords. More specifically, the present invention provides methodsmanaging metadata records related to content housed in unique, disparateor federated holdings in centralized or distributed environments. Thepresent invention also provides systems and methods for creating andmanaging metadata records using domain specific language, vocabulary andmetadata schema accepted by a community of users of unique, disparate orfederated databases in centralized or distributed environments. Suchenvironments can include content repositories.

BACKGROUND OF THE INVENTION

Metadata is simply defined as “data about data”. Metadata typicallydescribes the content, quality, condition, and/or other characteristicsof data. The purposes of metadata include assisting users to organizeand maintain an organization's or user community's internal or externalinvestment in spatial data, provide information about an organization'sor user community's data holdings to data catalogues, clearinghouses,and brokerages, and provide information to process and interpret datareceived through a transfer from a unique, disparate or federatedexternal source. Such a source can be centralized or distributed.

By 2005, more than fifty percent (50%) of large organizations will havemultiple sources of integration technology. As that proliferationoccurs, being able to recognize the use of metadata across differentdeployment platforms becomes extremely important. Coupled with thisproliferation, the explosive growth in personal computers (PCs),servers, Internet related software and web-based holdings has cultivateda need for companies to better understand their internal and externaldata needs. To better understand these needs, many gigabytes of datamust be collected and analyzed to arrive at the best way to service theuser.

Market and industry analysts alike, believe that the Internet will proveto be the most significant innovation in modern history since the lightbulb and automobile. With regard to the communication of consumerrelated data, the Internet will quickly surpass or encompass traditionalradio and television.

The method in which daily business operations are performed will bechanged forever due to this new technology. Many technology basedcompanies in the computer industry are scrambling to outline newproducts and services using and exploiting the Internet as a vehicle toincrease market share and revenue, while increasing productivity andcutting operational costs.

In an effort to meet the above needs of ingesting the vast amounts ofinformation on the web, companies have designed many browsers andmillions of web pages to access, retrieve and utilize this information.In addition to the Internet, companies have set up local “intranets” forstoring and accessing data for running their organizations. However, thesheer amount of available information is posing increasingly moredifficult challenges to conventional approaches.

A major difficulty to overcome is that information contained on the webor web pages are often dispersed or distributed across the network atmany sites. Networks themselves may be unique, disparate or federatedsituated in either centralized or distributed environments. It is oftentime-consuming for a user to visit all these sites. One conventionalapproach used to access this information more effectively is called asearch engine. A search engine is actually a set of programs accessibleat a network site within a network, for example a local area network(LAN) at a company or the Internet and World Wide Web. One program,called a “robot” or “spider,” pre-traverses a network in search ofdocuments and builds large index files of keywords found in thedocuments.

A user of the search engine formulates a query comprising one or morekeywords and submits the query to another program of the search engine.In response, the search engine inspects its own index files and displaysa list of documents that match the search query, typically ashyperlinks. When a user activates one of the hyperlinks to see theinformation contained in the document, the user exits the site of thesearch engine and terminates the search process.

Examples of various search engine methods include:

Brin et al., U.S. Pat. No. 6,678,681, Gomes et al., U.S. Pat. No.6,615,209, and Bharat et al., U.S. Pat. No. 6,526,440 discloses varioussearch engine strategies and data extraction methods where the databaseitself is the Internet or network of websites such as the World WideWeb.

Search engines, however, have their drawbacks. For example, a searchengine is oriented to discovering textual information only both weightedand non-weighted. In particular, they are not well-suited to indexinginformation contained in structured or unstructured databases, such as,relational databases, voice related information, audio or video relatedinformation, and metadata. Moreover, mixing data from incompatible datasources is difficult in conventional search engines.

Another disadvantage with conventional search engines is that irrelevantinformation is aggregated with relevant information. For example, it isnot uncommon for a search engine on the web to locate hundreds ofthousands of documents in response to a single query. Many of thosedocuments are found because they coincidentally include the same keywordin the search query. Sifting through search results in the thousands,however, is a daunting task.

Accordingly, inventors of the present invention have determined thatthere is a need to be able to effectively collect the data and/orprovide useful information indicative of events occurring on the web ina specified format that will speed up the collection of data, identifymore clearly what data is required, and capture information about thedata to make reporting more accurate. This specified format forcollection is also changeable and/or expandable. For example, data whichindicates where a user has been in prior sessions may be useful indesigning future products accessible via and for the web. The inventorsof the present invention have also determined that there is a need for aconvergence platform architecture, system and methods to support andanalyze Internet, electronic learning and/or electronic commerce dataover or from the World Wide Web.

Inventors of the present invention have further determined that there isthe need for a convergence platform architecture, system and methodsused to correlate user, application, and access functions. Further, itis also determined that there is a need to provide tool sets that caneasily communicate with, or become subsets of, an existing scaleabledata warehouse to provide Internet decision support, electronic learningand information management. Unfortunately, conventional architecturesand/or techniques are unable to organize and present this information inan efficient manner. Many attempts in the prior art include thefollowing:

Ignat, et al., in U.S. Pat. No. 6,611,838 discloses a method of managingmetadata via a metadata exchange platform that allows for asynchronization of databases.

Armatis et al., in U.S. Pat. No. 6,697,822 discloses a method to updatedata files using metadata consisting of unique record identifiers.

Boothby et al., in U.S. Pat. No. 5,684,990 and Pet et al., in U.S. Pat.No. 5,835,912 discloses methods to synchronize update and transfer dataand data records of disparate databases.

Noble et al., in U.S. Pat. No. 5,634,053 discloses a method to create avirtual centralized database of a plurality of interconnected localdatabases.

Dockter et al., in U.S. Pat. No. 5,678,038 discloses the use of databaseschemas for the management of classification systems.

Lau et al., in U.S. Pat. No. 6,502,098 discloses of transferring datausing data table hierarchy.

With the advances in technology and the increase in the number ofapplications, the definition of “data” and the formats that data ispresented or housed in continues to grow. More generally, data isdefined as facts represented in a readable language such as numbers,characters, images, or other methods of recording on a durable medium.Data on its own carries no meaning. Empirical data are facts originatingin or based on observations or experiences. A database is a store ofdata concerning a particular domain. Data in a database may be lessstructured or have weaker semantics (built-in meaning) than knowledge ina knowledge base. Data and data formats include text, graphics, printdocument formats (PDF), spreadsheets, presentation slides, digitalstored video, objects, and digital stored audio to name only a few.Still, further complicating the definition of data is that, at times,can be combinations of the previously stated data and data format.

Due to the increasing complexity of unique, disparate or federated datawarehouses in both centralized and distributed environments, acentralized and declarative management of metadata or metadata recordsis essential for data warehouse administration, maintenance and usage.Metadata is usually divided into technical and semantic data about data.Typically, current approaches, including those technologies in thepreviously cited U.S. Patents, only support subsets of these metadatatypes, such as data movement metadata or multidimensional metadata forOn-Line Analytical Processing (OLAP).

OLAP is a category of applications and technologies for collecting,managing, processing and presenting multidimensional data for analysisand management purposes.

To further complicate the environment that the prior art fails in, thecurrent marketplace is inundated with proprietary legacy systems,expensive technology and a plethora of point products. Also, the conceptof “registries” is not new. Registries range from automotive partsinformation to registries for worldwide domain name archives. In today'scomputer world, registries, such as dictionaries and catalogues, havebeen around for a long time such as Novell's Directory, Microsoft'sActive Directory, and IBM mainframe catalogue. In the United States, theDo-Not-Call Registry is perhaps the best known registry today whereusers can list their telephone numbers and sales groups are required toinspect the list and not call the listed users. However, theseregistries address different objectives and business problems.

In particular, the interdependencies between technical and semanticmetadata have not yet been addressed sufficiently by the prior art. Therepresentation of these interdependencies form an important prerequisitefor the translation of queries formulated at the business concept levelto executable queries on physical data.

With regard to specific content housed in a plurality of unique,disparate or federated database environments, the prior art fails inthat technologies are directed towards content or a mixture of contentand metadata requiring dramatic usage of memory space, personnelinputting time and expensive equipment. Prior art systems such aslearning content management systems (LCMS), document management systemsor content management systems (CMS) all relate to content itself and thecontent is housed or synchronized in a centralized site.

The present invention provides for interoperability and increases theutilization of the content that metadata is related to. Embodiments ofthe present invention provide convergence platforms, systems and methodsthat are based on standards that are relevant to the users providingcontext to their jobs and organizations.

SUMMARY OF THE INVENTION

Broadly defined, a metadata schema is at least one set of metadataspecifications, parameters and standards combined with at least one setof domain specific language and vocabulary both sets accepted by acommunity of users of unique, disparate or federated databases incentralized or distributed environments.

An embodiment of the present invention discloses a method to provide ametadata convergence platform comprising the steps of:

-   -   establishing at least one metadata schema;    -   creating at least one metadata record based on the at least one        metadata schema;    -   delivering the created at least one metadata record to a user.

A exemplary embodiment of the present invention provides said deliveringstep in formats such as user accessible databases, repositories, digitalarchives, analog archives or digital holdings.

Quality control of metadata output is now an important process that theprior art does not fully address. Quality control can include but is notlimited to review, edit modification, security screening, privacy,filtering and other document control or access control measures.

Another embodiment of the present invention discloses a method toprovide a metadata convergence metadata management system comprising thesteps of:

-   -   establishing at least one metadata schema;    -   creating at least one metadata record based on the established        at least one metadata schema;    -   submitting the created at least one metadata record to a staging        area database for quality control acceptance;    -   delivering the accepted, created at least one metadata record to        a user.

An additional embodiment of the present invention discloses methods toprovide unique metadata management methods that are directed towardsmetadata related to content itself rather than directed to specificcontent housed in a plurality of unique, disparate or federated databaseenvironments. Prior art systems such as learning content managementsystems (LCMS), document management systems or content managementsystems (CMS) all relate to content itself or content housed orsynchronized in a centralized site.

Using such methods of the present invention provides a method for a userto economically and quickly poll or search created, accepted metadatabased on established metadata schema.

Characteristics of metadata schema include but are not limited tostandards, rules, specifications, parameters, attributes, semantics,vocabulary, semantics and jargon accepted by a community of users ofunique, disparate, or federated holdings in centralized or distributedenvironments.

An embodiment of the present invention discloses a method to provide asearchable metadata convergence platform comprising the steps of:

-   -   identifying characteristics related to at least one metadata        schema;    -   creating at least one metadata record based on the identified        characteristics;    -   submitting the created at least one metadata record to a staging        area database for quality control acceptance;    -   delivering the accepted created at least one metadata record to        a user;    -   polling said delivered metadata record;    -   submitting polling results to the user.

It is also contemplated by the teachings of the present invention toinclude the automatic creation of metadata records related to thecontent of established unique, disparate or federated holdings.

An embodiment of the present invention has said delivering step as auser accessible database holding at least one metadata record.

Another embodiment of the present invention has said polling as akeyword search query.

Yet another embodiment of the present invention has said submittingpolling results as a display on a user's computer monitor.

An embodiment of the present invention discloses a method to provide ametadata convergence platform comprising the steps of:

-   -   identifying at least one metadata schema;    -   automatically ingesting metadata into at least one metadata        record based on the at least one metadata schema;    -   delivering the at least one metadata record to a user.

It is further contemplated by the teachings of the current invention todynamically generate metadata records based on created or establishedmetadata schema. Such generation utilizes standards and database tags,including but not limited to vocabulary, and servlets, accepted by acommunity of users of unique, disparate or federated database holdings.Servlets include but are not limited to programs that extend thefunctionality of a given environment. In terms of learning environmentsand web applications, servlets are to Web Servers what applets are forWeb Browsers: just as applets extend the functionality of a browser, sodo servlets (typically written in Java) add functions to Web Servers.Servlets are generated using special development kits such as deliveredwith the XML tools.

An embodiment of the present invention discloses a method to provide ametadata convergence platform comprising the steps of:

-   -   selecting at least one established metadata schema;    -   dynamically generating at least one metadata record using the        said metadata schema;    -   delivering the generated at least one metadata record to a user.

The user environment is inundated with proprietary legacy systems,expensive technology and a plethora of point products.

To address these business problems, it is further contemplated by thepresent invention that established metadata schema or standards-basedapproaches include but are not limited to XML, SCORM, Web Services, RDF,and OWL as generally defined in the following paragraphs. XML,eXtensible Markup Language. A widely used standard from the World WideWeb Consortium (W3C) that facilitates the interchange of data betweencomputer applications. XML is similar to the language used for Webpages, the HyperText Markup Language (HTML), in that both use markupcodes (tags). Computer programs can automatically extract data from anXML document, using its associated document type definition (DTD), is acollection of XML declarations that, as a collection, defines the legalstructure, elements, and attributes that are available for use in adocument that complies with the DTD as a guide.

SCORM, Sharable Content Object Reference Model. SCORM is a series ofe-learning standards and specifications that specify ways to catalogue,launch and track course objects. SCORM is further described in thedetailed description of the invention.

Web Services. Web-based applications that can dynamically interact withother Web applications using an XML message protocol (XMLP) such as SOAPor XML-RPC. SOAP (Simple Object Access Protocol) is a lightweightprotocol for exchange of information in a decentralized, distributedenvironment. It is an XML based protocol that consists of three parts:an envelope that defines a framework for describing what is in a messageand how to process it, a set of encoding rules for expressing instancesof application-defined datatypes, and a convention for representingremote procedure calls and responses. XML-RPC is a specification and aset of implementations that allow software running on disparateoperating systems, running in different environments to make procedurecalls over the Internet. It's remote procedure calling using HTTP as thetransport and XML as the encoding. XML-RPC is designed to be as simpleas possible, while allowing complex data structures to be transmitted,processed and returned.

RDF, Resource Description Framework, is a language for representinginformation about resources in the World Wide Web. It is particularlyintended for representing metadata about Web resources, such as thetitle, author, and modification date of a Web page, copyright andlicensing information about a Web document, or the availability schedulefor some shared resource. However, by generalizing the concept of a “Webresource”, RDF can also be used to represent information about thingsthat can be identified on the Web, even when they cannot be directlyretrieved on the Web. Examples include information about items availablefrom on-line shopping facilities (e.g., information aboutspecifications, prices, and availability), or the description of a Webuser's preferences for information delivery. RDF is intended forsituations in which this information needs to be processed byapplications, rather than being only displayed to people. RDF provides acommon framework for expressing this information so it can be exchangedbetween applications without loss of meaning.

OWL, Web Ontology Language is intended to be used when the informationcontained in documents needs to be processed by applications, as opposedto situations where the content only needs to be presented to humans.OWL can be used to explicitly represent the meaning of terms invocabularies and the relationships between those terms. Thisrepresentation of terms and their interrelationships is called ontology.

Non-limiting definitions of examples of emerging standards fordescribing, promoting and discovering these services are: ebXML, UDDI,WSDL, and Sun ONE are major implementations of the concept. The goal isto enable one application to find another on the Internet that providesa needed service and to seamlessly exchange data with it. Generaldefinitions for ebXML, UDDI, WSDL and Sun ONE follow: ebXML. ElectronicBusiness using eXtensible Markup Language is a modular suite ofspecifications that enables enterprises of any size and in anygeographical location to conduct business over the Internet. UsingebXML, companies now have a standard method to exchange businessmessages, conduct trading relationships, communicate data in commonterms and define and register business processes.

UDDI. \Universal Description, Discovery and Integration protocol. Adirectory model for web services. UDDI is a specification formaintaining standardized directories of information about web services,recording their capabilities, location and requirements in a universallyrecognized format.

WSDL. Web Services Description Language. The standard format fordescribing a web service. Expressed in XML, a WSDL definition describeshow to access a web service and what operations it will perform.

Sun One. Sun Open Net Environment (Sun ONE) is Sun's standards-basedsoftware vision, architecture, platform, and expertise for building anddeploying services on demand.

Another embodiment of the present invention discloses a method toprovide metadata a convergence platform comprising the steps of:

-   -   selecting at least one established metadata schema;    -   dynamically generating at least one metadata record using the at        least one established metadata schema;    -   delivering the at least one metadata record to a user accessible        database.

In various computing environments such as the World Wide Web, there willbe a need to use metadata from multiple schemas. It is contemplated bythe present invention that the convergence platform of the presentinvention can be characterized as a “semantic web”. Semantic web can begenerally defined as an abstract representation of data accessible viathe World Wide Web, using standards such as RDF. Such a semantic web isan extension of the current web in which information is givenwell-defined meaning, better enabling computers and users to work incooperation. Such a platform provides a common framework for expressinginformation so that data can be exchanged between applications withoutloss of meaning.

Here the concept that metadata schema is based on data tags,specifications and standards accepted by a community of users of unique,disparate or federated database holdings in centralized or distributedenvironments expands the scope of the present invention by addressingmultiple import and export metadata schemas.

Yet another embodiment of the present invention discloses a method toprovide a import-export metadata convergence platform comprising thesteps of:

-   -   selecting at least one import metadata schema;    -   generating at least one import metadata record using the at        least one import metadata schema;    -   submitting the at least one import metadata record to a metadata        conversion staging area;    -   selecting at least one export metadata schema;    -   converting the at least one import metadata record into at least        one export metadata record based on the at least one export        metadata schema;    -   delivering the at least one export metadata record to a user.

Another embodiment of the present invention discloses a method toprovide a semantic web metadata convergence platform comprising thesteps of:

-   -   selecting at least one import metadata schema;    -   generating at least one import metadata record using the at        least one import metadata schema;    -   submitting the at least one import metadata record to a metadata        conversion staging area;    -   selecting at least one export metadata schema;    -   converting the at least one import metadata record into at least        one export metadata record based on the at least one export        metadata schema;    -   submitting the at least one export metadata record to a user.

Again to review, metadata schemas can be selected, established orcreated by a community of users of unique, disparate or federatedholdings in centralized or distributed environments. For example, ametadata schema can be selected from already established schemas basedon standards and specifications accepted by a community of users such asSCORM. Metadata schema can be established by selecting an alreadyestablished schema and also selecting a set of vocabulary, standards orspecifications used and accepted by a community of users.

An example of a user established metadata schema could include agovernment entity selecting SCORM and also a set of entity specificvocabulary such as in-house jargon.

A final example is where the community of users initially selectsstandards, rules, attributes, vocabulary, specifications and other datarelated semantics to create a new, user community unique schema. Anexample of created metadata scheme could include the time when SCORM wasfirst made. Here the initial concept was that metadata schema is createdon data tags, specifications and standards accepted by a community ofusers of unique, disparate or federated database holdings in centralizedor distributed environments controlled by the users.

An embodiment of the present invention has the selected, established orcreated metadata schema containing SCORM as at least a subset of theschema.

Another embodiment of the present invention has the selected,established or created metadata schema containing RDF as at least asubset of the schema.

In accordance with another exemplary embodiment of the presentinvention, the selected, established or created metadata schema has atleast one existing schema as at least a subset of the selected,established or created metadata schema.

Furthermore, in accordance with another embodiment of the presentinvention, the at least one existing schema as at least a subset of theselected, established or created schema is chosen from the groupconsisting of SCORM, RDF, XML schemas, XML based schemas, OWL, UDDI, SunOne, WSDL, and ebXML.

Yet another embodiment of the present invention has the selectedmetadata schema is chosen from the group consisting of SCORM, RDF, XMLschemas, XML based schemas, OWL, UDDI, Sun One, WSDL, and ebXML.

In accordance with another embodiment of the present invention has theestablished metadata schema chosen from the group consisting of SCORM,RDF, XML schemas, XML based schemas, OWL, UDDI, Sun One, WSDL, andebXML.

In accordance with another embodiment of the present invention, theimport metadata schema is selected from the group consisting of SCORM,RDF, XML schemas, XML based schemas, OWL, UDDI, Sun One, WSDL, andebXML.

Furthermore, in accordance with another embodiment of the presentinvention, the export metadata schema is selected from the groupconsisting of SCORM, RDF, XML schemas, XML based schemas, OWL, UDDI, SunOne, WSDL, and ebXML.

Still further, in accordance with another embodiment of the presentinvention, the established metadata schema is selected from a group ofpreviously created metadata schemas created by a community of databaseusers.

In accordance with yet another embodiment of the current invention thesaid selecting step is a creating or establishing function.

Furthermore, in accordance with another embodiment of the currentinvention, the said establishing step incorporates a selecting orcreating function.

Still further, in accordance with another embodiment of the presentinvention said submitting step is a delivering function.

Furthermore, in accordance with another embodiment of the presentinvention said delivering step is a submitting function.

DETAILED DESCRIPTION OF THE INVENTION

The embodiments of the present invention provide web-based convergenceplatform tools where the tools are used to manage the metadata about thecontent, using the standards accepted or adopted by a community ofubiquitous or diverse users of unique, disparate or federated holdingsin centralized or distributed environments rather than managing thecontent itself directly with these tools.

Briefly, one of the embodiments of the present invention contemplatesthe design, creation or establishment of at least one metadata schema.

A non-limiting example of a metadata schema includes the description ofthe structure and the rules a document must satisfy for SGML (StandardGeneralized Markup Language). SGML is a set of standards for how tospecify a document markup language or tag set. SGML is not in itself adocument language, but a description of how to specify one. It is ametalanguage. HTML and XML are examples of SGML-based languages or XMLdocument types.

Again, using XML only as a non-limiting example, XML allows us to freeinformation from proprietary software and systems. XML is not so much alanguage as a standardized set of rules for adding structure to any formof data using a system of markup tags. Anyone can create their ownmarkup vocabulary (called an XML Schema), and XML ensures that thestructure will be intelligible to anyone else who consults the XMLschema document. More importantly, referring to an XML schema enablesXML-aware software to automatically manipulate the data without needingadvance knowledge of the structure.

The metadata schema comprises the formal declaration of the elementsthat make up a metadata record, their mutual coherence, meaning anddocumentation as drawn up for content type such as text, a document,information model such as a graphic, a table of information or a chart.

Metadata schema is, for example, more flexible than lone DTD files(files that define the elements and data structure contained in an XMLdocument). Because metadata schemas are more flexible, they can alsocontain rules for content or data types like dates, numbers, bit maps,file extensions, etc.

Another component of the present invention is the registration ofmetadata which is differentiated from “metadata tagging tools” and“authoring tools”. Metadata tagging tools are used to publish metadatarelated to product records such as card catalog systems that librarianscreate to catalog books. Authoring tools are used by subject matterexperts to create content to be tagged such as a book author creating atable of contents for a publication. These prior art tools deal withcontent that is archived in centralized storage arenas that requirestandards that are unique to the storage arena itself rather than theuser.

The present invention is differentiated from the prior art that theregistration tools contemplated by embodiments of the present inventionallow users to create metadata that is centralized and can be shared bymultiple users pulling content from unique, disparate or federatedholdings in centralized or distributed environments using thecharacteristics accepted or adopted by a community of diverse users.

Another embodiment of the present invention provides for methods to useseveral means of locating or accessing information.

A search could include any combination or number of parameters orattributes that were defined in the registration or metadata schemaformation process. For example, in an academic learning environment,learning parameters could be used such as subject topic, key word,learning resource type, and learning objective as registered by thecommunity of users.

Search methods of the present invention allow users to poll previouslycreated, established or managed metadata using the standards alreadyaccepted or adopted by a community of ubiquitous or diverse users ofunique, disparate or federated holdings, rather than polling only thecontent itself.

An example of a created web-based metadata system incorporating theembodiments of the present invention includes a system that enablesregistering, editing, deleting, updating, providing review process (e.g.recommendation, rejection, communication), searching, querying, sharing,harvesting, gathering, classifying, locating, exporting, presentingstandards-based and domain specific metadata for accessing, collecting(packaging), sharing, delivering, presenting and launching (opening)unstructured data and structured information related to the managedmetadata. The registration process related here includes the ability fortagging metadata and/or importing standards-based, domain specificmetadata.

Additionally, the collection and management of multiple metadata withassociated structured and unstructured information is contemplated bythe present invention. The convergence platform system contemplated bythe present invention provides duplication processes, definabletemplates, metadata registration and management methods.

It is further contemplated that the systems contemplated by the presentinvention provide exporting capabilities of metadata, “collections” ofmetadata and data in standards-based, interoperability and communicationexchange formats such as XML schemas.

More importantly, the exemplary created metadata management system ofthe present invention provides for manipulation of the “collection” (akapackages) of metadata, domain specific vocabulary, semantics, objectsand associated data.

The exemplary convergence platform systems contemplated by the presentinvention provides the ability to perform bi-directional communicationsuch as query, search, gathering, push, modify, and update with otherunique, disparate or federated systems in centralized or distributedenvironments.

The architecture of the present invention performs all above functionsacross multiple types of metadata such as the following: objective,subjective, and digital rights; layers of unstructured data such asinformation or content in multiple formats, learning objects andknowledge; and structured data such as data, metadata and/or metadataschema within databases.

The exemplary systems and methods of the present invention provide theability to be connected in a federated network architecture ofregistries and repositories and perform all of the above functions andstandards-based interoperability in a federated environment.

An example of a federated environment includes the diverse grouping ofagencies, departments, and offices of the governing bodies of the UnitedStates. The Department of Defense (DOD) and the White House Office ofScience and Technology Policy (OSTP) launched the Advanced DistributedLearning (ADL) Initiative in November 1997. The mission of the ADLinitiative is to provide access to the highest quality education andtraining, tailored to individual needs, delivered cost effectivelyanytime and anywhere. The ADL Initiative aims to accelerate large-scaledevelopment of dynamic and cost-effective learning software and systemsand to stimulate the market for these products. This will help meet theexpanding education and training needs of government, academia andindustry. As a foundation for accomplishing those goals, ADL's SharableContent Object Reference Model (SCORM) aims to foster creation ofreusable learning content as “instructional objects” within a commontechnical framework for computer and Web-based learning.

SCORM describes a user accepted technical framework by providing aharmonized set of guidelines, specifications, and standards based on thework of several distinct e-learning specifications and standards bodies.These organizations continue to work with ADL, developing and refiningtheir own e-learning specifications and standards and helping to buildand improve SCORM.

An embodiment of the present invention includes the incorporation ofSCORM as a member of the standards accepted or adopted by a community ofdiverse users of disparate or federated holdings. An example of such acommunity may include the following agencies and departments of theUnited States Government:

-   -   Patent and Trademark Office (USPTO);    -   Internal Revenue Service (IRS);    -   National Institutes of Health (NIH);    -   Department of Defense (DOD); and    -   Department of Homeland Security.

Another embodiment of the present invention includes the creation of ametadata based semantic registry system is an enterprise softwareapplication format providing convergence technology that providescontent interoperability.

Examples of SCORM community requirements and of a Metadata BasedSemantic Registry System (MBSRS) follows:

EXAMPLE 1 Training Technology Development (TTD)

Design and develop an advanced distributed learning (ADL) registry andrepository architecture and associated user interfaces to supportdistributed and federated computing terrorism training repositories.

The architecture must be Shareable Content Object Reference Model(SCORM) 1.3 conformant.

The architecture must be based on a collection of distributed serviceswith Web interfaces and an open component communications model that isconsistent with emerging computing and communication infrastructures.

The architecture must support:

-   -   content identifier, locator, reference, versioning, search and        query;    -   content management, sharing, and delivery; and    -   digital rights management, information assurance, and security.

The architecture must provide the capability to federate existing(disparate) SCORM and non-SCORM conformant content repositories.

The architecture must support content object reuse and establish modelsand procedures such that training materials produced by any agency willbe available for reuse across the community.

The architecture must perform all functions across multiple types ofmetadata (e.g., objective, subjective, rights, etc.) and layers ofobjects (e.g. learning, content, and knowledge).

The architecture must support customization of information based ondomain, for example:

-   -   federal, state, and local;    -   homeland defense, homeland security, and emergency response;    -   standards organizations and bodies;    -   federal, state and local sources for training; etc and unique        taxonomies within those domains.

The architecture must support establishing and maintaining acustomizable metadata framework spanning all identified domains andassociated training tasks.

The architecture will be accessible via standard industry web browsersoperating on person computer systems with the following minimum systemrequirements—Pentium II/III or equivalent, 233 MHz, 128 MB RAM, audioand video capable, 16× CD-ROM, 56K modem, with Windows 98, ME, 2002, orXP Operating System.

EXAMPLE 2 Metadata Based Semantic Registry System Description andRequirements

The metadata based semantic registry system (MBSRS) is an enterprisesoftware application and convergence technology that provides contentinteroperability. MBSRS enables the rapid non-programmatic developmentalong with the deployment of standards-based and domain specificmetadata registries. Additionally MBSRS a federated sharable contentnetwork architecture. MBSRS further provides customizable userinterfaces, business processes, accompanying software codes andcommunication protocols to facilitate interoperable registration,quality assurance, publishing, search, discovery, packaging,distribution. The architecture yields a highly efficient exchange ofinformation, content and best practices between organizations, systemsand people. MBSRS is horizontal market application designed to meetmarket needs for performance support applications. The diverse usageareas for MBSRS include distributed registry-repository systemsdevelopment, metadata intensive-dependent application development,performance support, knowledge management, eLearning, advanceddistributed learning, document/content management, electronicpublishing, information, and clearing houses. Furthermore, the MBSRSprovides for digital asset management, content-enabling applicationinfrastructure and networks.

MBSRS architecture is based on industry standard open componentcommunications model that is consistent with emerging computing andcommunication infrastructures. MBSRS environments can include web-basedand database environments that are OS platforms and network agnostic.The architecture can deal with multiple types of metadata, differenttypes of XML schemas and different layers of content.

MBSRS is comprised of three integrated user components: Metadata SchemaDevelopment (MSD); Metadata Record Creation (MRC); and MRC Searching.

MSD provides the interfaces and processes for non-programmatic users(normally Information Architecture/Domain Information Experts) todevelop and deploy the metadata database for the metadata registry. MRC,provides the interfaces and processes for non programmatic users (usedby subject matter experts and content providers) to register, providequality assurance and publish metadata (stored within the developed anddeployed metadata database) and content (stored in distributedrepositories, systems and organizations) described and pointed to(referenced) by the metadata. MRC Searching, used by all end users isused to query the metadata stored within the metadata database to searchfor distributed content, access the content, generate metadata (in XML)of the content in various schemas, and create packages for transportinginto other systems.

To deploy the metadata registries system non-programmatic users use asimple three-step process:

First, setup the metadata framework of the metadata database and makethe system operation through MSD.

Second, Subject Matter Experts and Content Providers being the processof registering the metadata of distributed objects within the metadatadatabase through MRC. MRC also provides the integrated quality controlprocess of the metadata before it is accepted into the metadatadatabase. The second is an on-going process.

Third, end users access MRC Searching to search, retrieve, access andshare content and related metadata from the metadata database.

MSD—The system provides the ability for users without technicalbackground and/or computer programming skills (i.e. non-programmaticusers) to create, establish, maintain, modify and administer a metadatadatabase through easy to use web interfaces and built-in businessprocesses. The metadata database can be preloaded with standards-basedmetadata and accompanying metadata framework, that incorporates astandards-based metadata and domain specific metadata and accompanyingmetadata framework, and facilitates the management, representation,import/export of the in multiple schemas, without the need for anyprogramming or technical/technology intervention. The metadata andmetadata framework include industry specification and reference modelsfor metadata and content interoperability and customizable metadata andmetadata framework, unique taxonomies, ontology, organizationalobjectives and keyword vocabularies spanning all identified domains andapplication tasks. The system business process include the ability fornon-programmatically:

Adding and creating, importing/exporting, modifying, ‘taxonomies andontology’ parameters for developing, deploying and maintaining themetadata database of the registry-repository system.

Adding, creating, importing/exporting, modifying, values of ‘metadataattributes’ and for developing, deploying and maintaining the metadatadatabase of the registry-repository system.

Adding and creating, importing/exporting, modifying, ‘organizationalobjectives’ parameters for developing, deploying and maintaining themetadata database of the registry-repository system.

Adding and creating, importing/exporting, modifying controlledvocabulary parameters for developing, deploying and maintaining themetadata database of the registry-repository system.

MSD provides additional functionality to mange users, user groups andalso manage URL of external repositories. The metadata and metadataframework of the metadata database created using MSD is automaticallyreflected in the user interfaces of MRC and MRC Searching.

MRC provides access to metadata registration templates and processes toenable registering, editing, deleting, updating, providing reviewprocess (e.g. recommendation, rejection, communication) of metadata ofdistributed content. The registration process includes the ability forimporting standards-based and domain specific metadata in differentschemas and collection of multiple metadata and associated content. MRCadditionally provides metadata quality control process, duplicationprocess and life cycle management processes.

MRC Searching provides searching, querying, sharing, harvesting,gathering, classifying, locating, exporting, presenting standards-basedand domain specific metadata for accessing, collecting (packaging),sharing, delivering, presenting and launching (opening) distributedcontent related to the metadata registered and stored within themetadata database.

In addition, MRC Searching provides exporting capabilities of metadataand the ‘collection’ of metadata and content in standards-basedinteroperability and exchange formats (different XML schema). The exportformats (schemas) incorporate standards-based metadata withcustomizations and extensions to standards that include domain specificmetadata, taxonomies, ontology and organizations objectives and keywordvocabularies. MRC Searching provides for manipulation of the‘collection’ (a.k.a. packages) of metadata and associated data.

The system provides the ability to be connected in a federated networkarchitecture of registries and repositories and perform all of the abovefunctions and standards-based interoperability in a federatedenvironment. MBSRS provides the ability to perform bidirectionalcommunication (e.g. query, search, gathering, push, modify, update) withother systems.

EXAMPLE 3 Building Metadata Schema

Descriptive framework built accordance with an embodiment of the presentinvention has metadata schema designed to align with emerging standardsfor labelling information, including the SCORM, IEEE LOM, and themetadata elements and vocabularies specific to an organization. Anexample of features of building metadata schema include two items foradministration and review functions. The administration feature allowsthe user to manage user accounts, build the taxonomic structure, createand manage the keywords, using both closed or open vocabulary, integrateperformance or learning standards, compose the metadata attributes, viewobjects associated with specific attributes, and manage the stagingdatabase. The review feature allows the Administrators to reviewmetadata records in the a staging area to perform quality controlmeasures.

EXAMPLE 4 Registration of Metadata Using SCORM

Embodiments of the present invention allow users register the metadataabout objects. The registration process begins by identifying anobject's significant attributes. These attributes are captured in themetadata record (form containing the descriptors about the object).Status functions contemplated by the present invention allow the userwho submitted registration forms to track their submitted objects. Theimport feature permits the user to browse the local machine or the localarea network for SCORM conformant objects in the form of SCORMconformant metadata XML documents or SCORM conformant content packages.Once uploaded, these records reside in the temporary staging area untilreviewed by the user. The template feature provides the tools to createa personal or public template used for multiple objects with similarmetadata attributes. While creating a content package, the user can viewthe objects within the package being built and defined.

EXAMPLE 5 Searching Submitted Metadata Records and XML Conversion ofObjects

Embodiments of the present invention enables the discovery andcontextual utilization of objects. Four possible methods currentlycontemplated by the present invention for locating and accessing objectsbased on the metadata as searchable properties. Each method of search,i.e., Taxonomic Path (Category), Keyword, Objective, and Attribute,provides an Object List based on relationships through metadata. Usersuse the Category (Taxonomic Path), Keyword, Objective, and Attributesearch in polling contemplated by the present invention.

Additionally, an embodiment of the present invention allows for themethods to create XML documentation for objects in real-time. Adesignated user can also locate objects from multiple search queries,select appropriate distributed or centralized objects and create datapackets to be imported into other applications. Users can also structurethe order of those objects to position for sequencing within systemslike an LMS or LCMS.

EXAMPLE 6 SCORM Content Packages as Data Packets

The content packaging defines a standardized method to exchange content.A Content Package is created to share content among other SCORMconformant applications or systems. A Content Package is an abstractdescription of a unit of useable (and reusable) objects. The mainelements of a Package are: a Manifest file, the physical objects and theXML metadata file of the physical objects.

If the physical objects are distributed then the XML metadata file alsocontains the location information. A manifest tag is contemplated by thepresent invention to serve a similar role to a “packing slip” by listingall objects used by the content package. The physical objects are acollection of objects physically accompanied with their metadata andincluded within a content package.

Embodiments of the present invention provide methods to create a contentpackage by adding objects to a package in a zip file, arranging theorder of the objects within the content package, and describing thecontents of the package based on IMS specifications as part of SCORM.IMS is an acronym for Instructional Management System. A project withpartners from academic, commercial and government organizations which isputting in place the essential underpinnings for Internet-basededucation. The goal of the project is the widespread adoption of a setof specifications that will allow distributed learning environments towork together.

EXAMPLE 7 Metadata Framework—Standards-based (SCORM) and Custom

Embodiments of the present invention provides methods for the immediateimplementation of the following mandatory SCORM elements:

-   -   Title    -   Description    -   Location    -   Version    -   Status    -   Catalog Entry and Number    -   Metametadata-Identifier, Contribute, Language    -   Format    -   Cost    -   Copyright and Other Restrictions

Additionally the following optional SCORM and domain specific metadatacan be readily available. For example the sample list includes but isnot limited to:

-   -   Aggregation Levels    -   Keywords    -   Contribute-Role, vCard, Date    -   Language    -   Coverage    -   Size    -   Technical Requirement    -   Installation Remarks    -   Other Platform Requirements    -   Duration    -   Intended End User    -   Typical Age Range/Proficiency Level    -   Typical Learning Time    -   Taxonomic Paths    -   Relation-Kind-Resource    -   Annotation-Description    -   Accessibility-Access Profile

Integration of additional organization metadata elements is alsoprovided for such as:

-   -   Available Delivery Media    -   Subject Classification Structure    -   Essential Skills including Vocabulary    -   Resolution (For images)    -   Any other unique identifiers and unique metadata within the        organization.

Metadata can be incorporated into the metadata framework including butnot limited to:

-   -   Standard Source and Codes    -   Organizational Standards and Objectives    -   Competencies and Performance Support Objectives    -   Other metadata to enable a task oriented delivery of distributed        objects.

Again, the preceding examples were given as written illustrations ofnon-limiting embodiments of the present invention. One skilled in theart can appreciate the scope of the present invention. For example,SCORM used in an earlier example above stated a specific version. It isanticipated that all versions of SCORM are included but not limited tousage in various embodiments of the present invention.

It is further contemplated by yet another embodiment of the presentinvention to dynamically generate metadata records based on created orestablished metadata schema. Such generation may utilize servlets toperform processes that transform the metadata record into XML orappropriate format based on, but not limited to, standard and customvocabulary and taxonomy accepted by a community of users of unique,disparate or federated database holdings. Servlets include but are notlimited to programs that extend the functionality of a givenenvironment. In terms of learning environments and web applications,servlets are to Web Servers what applets are for Web Browsers: just asapplets extend the functionality of a browser, so do servlets (typicallywritten in Java) add functions to Web Servers. Servlets are generatedusing special development kits such as delivered with the XML tools.

Still further, another embodiment discloses computer programs that canautomatically extract data from an XML document, using its associateddocument type definition (DTD) or XML Schema Definition (XSD) which is acollection of XML declarations that, as a collection, defines the legalstructure, elements, and attributes that are available for use in adocument that complies with the DTD or XSD as a guide.

Another embodiment of the present invention discloses a simple method toprovide a semantic web metadata convergence platform comprising thesteps of:

-   -   selecting at least one import metadata schema; and    -   generating at least one import metadata record using the at        least one import metadata schema.

Given such simple methodology, various embodiments of the presentinvention relate to desktop applications as an automated process. MSDprovides the interfaces and processes for non-programmatic users(normally Information Architecture/Domain Information Experts) todevelop and deploy the metadata database for the metadata registry. MRC,provides the interfaces and processes for non programmatic users (usedby subject matter experts and content providers) or automated systems toregister, provide quality assurance if necessary and publish metadata(stored within the developed and deployed metadata database) and content(stored in distributed repositories, systems and organizations)described and pointed to (referenced) by the metadata. MRC Searching,used by all end users or systems is used to query the metadata storedwithin the metadata database to search for distributed content, accessthe content, generate metadata (in XML) of the content in variousschemas, and create packages for transporting into other systems.

Yet a further embodiment of the present invention discloses that thesystems or processes contemplated by the inventors need not berestricted to web-based systems. he embodiments of the present inventionprovide convergence platform tools where the tools are used to managethe metadata about the content, using the standards accepted or adoptedby a community of ubiquitous or diverse users of unique, disparate orfederated holdings in centralized or distributed environments ratherthan managing the content itself directly with these tools.

Various embodiments of the present invention also reduce the need of theuser's computer skills. Further embodiments provide the ability forusers without technical background and or computer programming skills(i.e. non-programmatic users) or other systems to create, establish,maintain, modify and administer a metadata database through easy to useinterfaces and built-in business processes. The metadata database can bepreloaded with standards-based metadata and accompanying metadataframework, that incorporates a standards-based metadata and domainspecific metadata and accompanying metadata framework, and facilitatesthe management, representation, import/export of the in multipleschemas, without the need for any programming or technical/technologyintervention. The metadata and metadata framework include industryspecification and reference models for metadata and contentinteroperability and customizable metadata and metadata framework,unique taxonomies, ontology, organizational objectives and keywordvocabularies spanning all identified domains and application tasks. Thesystem business process include the ability for non-programmatically.

Continuing, another embodiment of the present invention provides theability to be connected in a federated network architecture ofregistries and repositories and perform all of the above functions andstandards-based interoperability in a federated environment. MBSRSprovides the ability to perform bi-directional communication (e.g.query, search, gathering, push, modify, update) with other systems ordevices.

If the physical objects are distributed then the XML metadata file alsocontains the location information. A manifest file containingappropriate tags is contemplated by the present invention to serve asimilar role to a “packing slip” by listing all objects used by thecontent package. The physical objects are a collection of objectsphysically accompanied with their metadata and included within a contentpackage.

Metadata housekeeping, tracking and reporting functions are greatlyenhanced. An embodiment of the present invention allows for an automaticpurge of data based on established parameters of the system. Forexample, the system could be configured to delete all the records thatare past a certain date. Still a further embodiment has the ability tooffer transaction based usage and can keep track of the queries thatwere executed, who executed them, what data was retrieved and if therewere any costs involved. This tracking information can be used fortransaction based services.

SCORM content allows for interactivity through JavaScript. A SCORM APIenables communication between the JavaScript within the content and thesystem in order to keep track of relevant data concerning the content,ie test scores and usage. Inherent is the capability to hold the datathat has been gathered from the SCORM content and the tracking ofnon-SCORM objects.

An aspect of an embodiment of the present invention also discloses theability to enforce Digital Rights of the objects in the system. Forexample, if the object contains metadata allowing certain rights, thesystem will abide by those rights. Additionally, the ability to reporton the contents of the registry is disclosed. For example, reporting thetype of content referenced in system or outlining the usage of thecontent. Alternative embodiments also disclose the ability to syndicate(publish) XML or RSS feeds to show availability (catalog) of contentaccessible by the system.

The following are additional non-limiting examples related to variousembodiments of the present invention.

EXAMPLE 8 SCORM Content Packages as Data Packets with Manifest File

The content packaging defines a standardized method to exchange content.A Content Package is created to share content among other SharableContent Object Reference Model (SCORM) conformant applications orsystems. A Content Package is an abstract description of a unit ofuseable (and reusable) objects. The main elements of a Package are: aManifest file, the physical objects and the eXtensible Markup Language(XML) metadata file of the physical objects.

If the physical objects are distributed then the eXtensible MarkupLanguage (XML) metadata file also contains the location information. Amanifest file containing appropriate tags is contemplated by the presentinvention to serve a similar role to a “packing slip” by listing allobjects used by the content package. The physical objects are acollection of objects physically accompanied with their metadata andincluded within a content package.

Various embodiments of the present invention provide methods to create acontent package by adding objects to a package in a compressed file,arranging the order of the objects within the content package, anddescribing the contents of the package based on IMS specifications aspart of Sharable Content Object Reference Model (SCORM). IMS is anacronym for Instructional Management System. A project with partnersfrom academic, commercial and government organizations which is puttingin place the essential underpinnings for Internet-based education. Thegoal of the project is the widespread adoption of a set ofspecifications that will allow distributed learning environments towork.

The Metadata Based Semantic Registry System (MBSRS) also providesmethods to package digital rights information along with InstructionalManagement System (IMS)/Sharable Content Object Reference Model (SCORM)metadata. For example, if the user chooses several objects and packagesthem together, the necessary digital rights information will be includedwithin the package.

The location metadata in the package to the content may point to thecontent contained in the package, the Uniform Resource Locator(URL)/Uniform Resource Identifier (URI) to content on the Internet, ormay contain an identifier such as a Digital Object Identifier (DOI), aMetadata Based Semantic Registry System (MBSRS) Identifier or analternative persistent identifier. The persistent identifiers like MBSRSID or DOI will be used to enable the tracking of access and usage of thecontent that has been distributed outside of the MBSRS system orfederated network.

EXAMPLE 9 Automated Object Registration

An embodiment of the present invention allow systems to automaticallyregister objects into the Metadata Based Semantic Registry System(MBSRS). Systems send eXtensible Markup Language (XML) document(s)and/or binary data containing metadata corresponding to the contents ofthe data that it describes into the MBSRS, the MBSRS processes the XMLand/or binary data and registers the object into the MBSRS. The actualdata may be moved into a designated content area, database or remainedunmoved and referenced by its location via an Uniform ResourceIdentifier (URI), Digital Object Identifier (DOI), or other identifier.The object is then accessible via the MBSRS.

EXAMPLE 10 Content Syndication

Another embodiment of the present invention provide methods that enablethe publishing of eXtensible Markup Language (XML) or ResourceDescription Framework (RDF) documents representing the contents of theMetadata Based Semantic Registry System (MBSRS). The documents areaccessible from a particular interface within the MBSRS, typically aUniform Resource Locator (URL). The document is processed eitherstatically (preprocessed) or dynamic based on parameters contained withthe URL string, exhttp://[server]/[name]?feedType=RSS&keyword=Headlines. This example willproduce a document based on the RDF Site Summary (RSS) schema of themetadata of the objects that have a keyword of “Headlines”. As moreobjects with the keyword “Headlines” get registered into the system, thecontents of the document will change to reflect the additional objects.This URL can be used by newsreaders, portals, or other systems.

EXAMPLE 11 Schema Transformation

Further embodiments of the present invention provide methods to enablethe schema transformation necessary to meet the needs of the requiredcommunication. For example, if a user or system requests an object fromthe system and requires it be in a certain format or schema, theMetadata Based Semantic Registry System (MBSRS) will give the requesterthe object's contents in that format or schema. An example of that wouldbe if the Uniform Resource Locator (URL) washttp://[server]/[name]?feedType=RSS&keyword=Headlines, the system wouldrespond with a document with a RDF Site Summary (RSS) schema, whilehttp://[server]/[name]?feedType=atom&keyword=Headlines, would respondwith a document with an atom schema. Atom is a format for syndicatingdata.

The system does this transformation not only for content syndication,but for all communication with other systems. For example, if anobject's schema uses the standard Learning Object Metadata (LOM)Institute of Electrical and Electronics Engineers (IEEE) 1484 schema,but needs to communicate with another system that does not conform tothese specifications the system can transform the schema to the formator schema of the other system. The system can also register objects frommultiple schemas.

EXAMPLE 12 Transaction Based Usage

Various embodiments of the present invention provide methods to enablethe tracking of accessed content by means of metadata derived from orcontained in the Metadata Based Semantic Registry System (MBSRS). Forexample, if a user or system accesses content that is referenced byobtaining it from an attribute of metadata that was stored within theMBSRS, the access will be tracked and the information of who, what, whenand how that content was accessed will be stored. This data will be usedfor billing and/or analysis purposes. Ad Hoc queries on the MBSRS willalso be tracked and that data can also be used for billing and/oranalysis purposed.

The MBSRS also provides methods to track the usage within the contentitself by utilizing the Sharable Content Object Reference Model (SCORM)Application Program Interface (API). For example, if the user accessedthe content and it is determined to be SCORM enabled, the system willprovide a SCORM API to allow the content's data to be stored in theMBSRS.

The MBSRS also provides methods to enforce digital rights of thecontent. The usage and cost rights of the content can be viewed and mustbe complied with prior to and during the access of the content. Forexample, if the user chooses the particular object and there arecorresponding digital rights, the user will be prompted to enter eithercredentials or payment information. This process is also accessible toautomated systems, although the payment information will be setup eitherprior to or in an automated fashion and digital rights will carry alongwith the content as metadata.

The MBSRS provides methods to distribute encrypted containers thatcontain digital rights information gathered from the MBSRS. Whenaccessed, prompts the user to enter credentials or payment information.Information can be relayed back to a main server for tracking access andusage.

EXAMPLE 13 Embedded Application

The Metadata Based Semantic Registry System (MBSRS) and all of itsfunctions can reside in a hardware device specifically designed for aparticular function. This hardware device can use the entire MBSRS asits foundational platform or utilize particular components of the MBSRSas additional functionality for the device. MBSRS can also be used as acomponent or foundation for a commercial or non-commercial application.For example, a proprietary application vender can choose to embed theMBSRS functionality into their application, that application can then bedistributed onto various platforms.

EXAMPLE 14 Reporting Capabilities

An embodiment of the present invention provide enables the reporting ofcontents within the Metadata Based Semantic Registry System (MBSRS),access of content and metadata, and billing information of the system.Such as, a user or administrator can run a report and see that John Doeregistered 20 objects in the last 30 days, he accessed 30 contentobjects, and owes a total of $5.25.

EXAMPLE 15 Expiration Process

Still another embodiments of the present invention provide methods toenable the expiration of data within the Metadata Based SemanticRegistry System (MBSRS) based on predetermined criteria. Since largeamounts of data can be automatically registered into the MBSRS, thesystem has the ability to automatically purge objects and theircorresponding data based on rules set by a user or administrator. As asample, if the system gets 1000 GB of data for the week consisting of15,000 objects. The system can be configured to delete the objects thathave an attribute “importance level” below 5, on a 1-10 scale, whichwould decrease the amount of data in the system. The user/administratorcan also choose to archive the data into an alternative repository orfile system.

EXAMPLE 16 Computers and Alternate Hardware Devices

Hardware devices contemplated by the present can include but are notelimited to hardwired specialized components that do machine processingand/or devices containing known or future operating systems (e.g Linuxor Windows versions). Hardware contemplated by an embodiment of thepresent invention are selected from the group consisting of but notlimited to: personal digital assistants; portable music players; cellphones; smart phones; entertainment related digital equipment; hand-heldpersonal computers; personal computers; telecommunications equipment;and combinations or derivatives thereof.

EXAMPLE 17 MBSRS, DOI & SCORM Alternative Definitions

Metadata Based Semantic Registry System (MBSRS Identifier)—Object ID ofthe MBSRS Identifier Object in the MSSRS. The object can be referencedexternally by referencing the URL of the instance of MBSRS along withthe Object ID of the object. For example, to externally accessparticular content, the URL would look similar to this:http://[serverName]/[webapp]/?ID=192.168.0.5:13e3940:101862c2c5e:-7ffe.The object consists of the Internet Protocol (IP) address of the serverwhich the object was first registered along with a set of digits uniqueto that object. This identification mechanism can be changed and mayincorporate Digital Object Identifier (DOI).

Digital Object Identifier (DOI) is a system for identifying contentobjects in the digital environment. DOI's are names assigned to anyentity for use on digital networks. They are used to provide currentinformation, including where they (or information about them) can befound on the Internet. Information about a digital object may changeover time, including where to find it, but its DOI will not change.

Sharable Content Object Reference Model (SCORM) enabled or (SharableContent Object) SCO—Having the necessary handle within the content tocommunicate with a SCORM API. Usually consisting of embedded JavaScript,but may include other communication mechanisms.

EXAMPLE 18 Vehicle Fleet Information Service

Built upon various embodiments of the present invention, methods areprovided for managing large amounts of distributed multimedia contentthrough XML event ‘metadata’. Provided is a distributed registry forautomated cataloging and discovery of multimedia ‘event content’ overthe Internet. Event metadata is ‘registered’ by reading ‘tags’ withinthe XML stream received from each Video Event Data Recorder (VEDR) overa WiFi; cellular network; or other telecommunications network. Theresultant system places the multimedia event content and metadata intolocal and global repositories providing a platform for automatedreported such as: Event Review; Driver Feedback; Training; LearningManagement; and claims Handling functionalities.

Each Media Server at each fleet depot to automatically index and manageall event metadata as well as the rich media ‘event content’ as it isreceived from each VEDR.

Duplications are made of all event metadata from all fleet depot MediaServers as well as duplicate copies of all content from events definedas ‘critical’ such as an accident.

Still further, systems contemplated can be tailored to address therequirements of a vertical transportation market or an individual fleet.These market-specific requirements may include specific hardwarerequirements in the vehicle or at the depot. Or the requirements may bespecific applications such as driver identification, additional camerasor complex sensor integration. Additionally, various embodiments canalso be integrated at the ‘service platform’ level with other real-timefleet management systems to provide gapless satellite & cellularcoverage. The service can also be integrated with E-911 & Automated CallNotification (ACN) systems—including a ‘First Notice of Loss’notification to fleet operators and insurance companies when an event oremergency occurs.

The preceding additional examples were given as written illustrations ofnon-limiting embodiments of the present invention. One skilled in theart can appreciate the scope of the present invention.

Unless otherwise indicated, all numbers expressing quantities ofingredients, properties such as data, database parameters, reactionconditions, and so forth in the specification and embodiments are to beunderstood as being modified in all instances by the term “about.”Accordingly, unless indicated to the contrary, the numerical parametersset forth in the specification are approximations that may varydepending upon the desired properties sought to be obtained by thepresent invention. At the very least, and not as an attempt to limit theapplication of the doctrine of equivalents to the scope of theembodiments, each numerical parameter should at least be construed inlight of the number of reported significant digits and by applyingordinary rounding techniques. Notwithstanding, numerical ranges andparameters setting forth the broad scope of the invention areapproximations, the numerical values set forth are reported as preciselyas possible. Numerical values, however, inherently contain certainerrors necessarily resulting from the standard deviation found in theirrespective testing measurements.

The terms “a” and “an” and “the” and similar referents are used in thecontext of describing the invention and are to be construed to coverboth the singular and the plural, unless otherwise indicated herein orclearly contradicted by context. Recitations of ranges of values hereinare merely intended to serve as a shorthand method of referringindividually to each separate value falling within the range. Unlessotherwise indicated herein, each individual value is incorporated intothe specification as if it were individually recited herein. All methodsdescribed herein can be performed in any suitable order unless otherwiseindicated herein or otherwise clearly contradicted by context. The useof any and all definitions, examples, or exemplary language (e.g. “suchas”) provided herein is intended merely to better illustrate theinvention and does not pose a limitation on the scope of the inventionotherwise claimed. No language in the specification should be construedas indicating any non-claimed element essential to the practice of theinvention.

Groupings of alternative elements or embodiments of the inventiondisclosed herein are not to be construed as limitations. Each groupmember may be referred to and claimed individually or in any combinationwith other members of the group or other elements found herein. It isanticipated that one or more members of a group may be included in, ordeleted from, a group for reasons of convenience and/or patentability.When any such inclusion or deletion occurs, the specification is hereindeemed to contain the group as modified thus fulfilling the writtendescription of all Markush groups used in the appended embodiments.

Exemplary embodiments of this invention are described herein, includingthe best mode known to the inventors for carrying out the invention. Ofcourse, variations on those exemplary embodiments will become apparentto those of ordinary skill in the art upon reading the foregoingdescription. Accordingly, this invention includes all modifications andequivalents of the subject matter recited in the embodiments appendedhereto as permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the invention unless otherwise indicated herein orotherwise clearly contradicted by context.

In closing, it is to be understood that the embodiments disclosed hereinare illustrative of the principles of the present invention. Othermodifications that may be employed are within the scope of theinvention. Thus, by way of example, but not of limitation, alternativeconfigurations of the present invention may be utilized in accordancewith the teachings herein. Accordingly, the present invention is notlimited to that precisely as shown and described.

In addition, the embodiments of the present invention, withoutlimitation, can be used in research, product manufacturing, and dataaccess systems or used calibration systems as in accordance with theappropriate research, clinical trial, manufacturing or treatmentprotocols or procedures approved by the appropriate governinginstitutions having authority to recommend, approve, evaluate orregulate such protocols or procedures.

1. A method to provide a convergence metadata management systemcomprising the steps of: establishing at least one metadata schema;creating at least one metadata record based on the established at leastone metadata schema; submitting the created at least one metadata recordto a staging area database for quality control acceptance; deliveringthe accepted, created at least one metadata record to a user.
 2. Amethod to provide a searchable metadata convergence platform comprisingthe steps of: identifying characteristics related to at least onemetadata schema; creating at least one metadata record based on theidentified characteristics; submitting the created at least one metadatarecord to a staging area database for quality control acceptance;delivering the accepted created at least one metadata record to a user;polling said delivered metadata record; submitting polling results tothe user.
 3. A method to provide a metadata convergence platformcomprising the steps of: identifying at least one metadata schema;automatically ingesting metadata into at least one metadata record basedon the at least one metadata schema; delivering the at least onemetadata record to a user.